Skip to content

Remove obsolete fuzzing code #1896

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Apr 10, 2023
Merged

Conversation

Markoutte
Copy link
Collaborator

Description

The previous fuzzing code is obsolete now. Other languages have finished moving to new fuzzing platform. Only several classes are still used from the old module. Therefore, old module is renamed from utbot-fuzzer to utbot-java-fuzzing to clarify that is used only for java-specific fuzzing. Though, there are several things to do:

  1. Things like FuzzedValue, FuzzedType, etc. should be replaced by own implementations in specific languages (to get rid off classId transitive dependency).
  2. UtFuzzedExecution should be moved to some new place. This problem should be discussed with @EgorkaKulikov because summarization depends on it.

How to test

Automated tests

All fuzzing-related tests should pass as before.

Manual tests

All fuzzing-related tests should pass as before.

Self-check list

  • I've set the proper labels for my PR (at least, for category and component).
  • PR title and description are clear and intelligible.
  • I've added enough comments to my code, particularly in hard-to-understand areas.
  • The functionality I've repaired, changed or added is covered with automated tests.
  • Manual tests have been provided optionally.
  • The documentation for the functionality I've been working on is up-to-date.

@Markoutte Markoutte added ctg-refactoring Issue related to refactoring process comp-fuzzing Issue is related to the fuzzing labels Mar 6, 2023
@Markoutte Markoutte force-pushed the pelevin/remove_obsolete_fuzzing_code branch from 3f5c1e0 to 4e20de3 Compare March 9, 2023 06:23
@Markoutte Markoutte force-pushed the pelevin/remove_obsolete_fuzzing_code branch from 4e20de3 to 62d294b Compare March 27, 2023 10:23
@Markoutte Markoutte force-pushed the pelevin/remove_obsolete_fuzzing_code branch from 62d294b to 08438f6 Compare April 6, 2023 08:59
@Markoutte Markoutte force-pushed the pelevin/remove_obsolete_fuzzing_code branch from 08438f6 to 8ecb438 Compare April 10, 2023 06:01
@Markoutte Markoutte merged commit 246bea2 into main Apr 10, 2023
@Markoutte Markoutte deleted the pelevin/remove_obsolete_fuzzing_code branch April 10, 2023 08:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
comp-fuzzing Issue is related to the fuzzing ctg-refactoring Issue related to refactoring process
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants